Tandridge District Council
Tree
There is a problem
- 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order
Elgin Crescent Caterham
- reference
- 11/C&W T1
- name
- Elgin Crescent Caterham
- tree-preservation-order
- 11/C&W
- uprn
- address-text
- Elgin Crescent Caterham
- point
- POINT (-0.074480 51.288290)
- geometry
- MULTIPOLYGON (((-0.073821 51.289222,-0.073921 51.289106,-0.074030 51.289006,-0.074693 51.289210,-0.074874 51.288960,-0.075241 51.289076,-0.075313 51.288979,-0.074931 51.288876,-0.075004 51.288753,-0.074685 51.288659,-0.075038 51.288227,-0.075067 51.288205,-0.075393 51.288273,-0.075979 51.287527,-0.074740 51.287124,-0.074471 51.287584,-0.074156 51.287934,-0.073869 51.288272,-0.073724 51.288417,-0.073687 51.288399,-0.073663 51.288421,-0.072817 51.288862,-0.072611 51.289002,-0.072669 51.289028,-0.073821 51.289222)))
- notes
- organisation
- felled-date
- entry-date
- 1961-08-01
- start-date
- 1961-08-01
- end-date
How to fix this issue
Your dataset is missing the tree-preservation-order column.
The Tree guidance explains how to fix the issue:
tree-preservation-order
The reference for the tree preservation order that affects this tree.
Example: TPO1
How to improve Tandridge District Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL